Account linking with privacy keys

ABSTRACT

A computer system includes a security module programmed to generate a first privacy key for use with secure communications with a first web site, and a second privacy key for use with secure communications with a second web site, the first and second keys being different. The computer system also includes an identity module programmed to receive a request from the first web site for linking a first user account associated with the first web site with a second user account associated with the second web site, and the identity module being programmed to present a user with an option to link the first and second user accounts.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the United States Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND

As users continue to increase their reliance on online resources to conduct business and pleasure, the importance of protecting privacy and facilitating secure transactions grows. Encryption of information is one method for providing privacy and security in the online environment. One encryption method involves the use of a public key that is shared openly with others. The public key is used to encrypt a message that is sent to the owner of the public key. The owner then uses a secret key to decrypt the message. The use of advanced cryptography such as public keys functions to counter “phishing” attacks and provides a new level of protection for online users.

One of the potential disadvantages of this type of cryptography is that when a public key is reused at many online sites, the public key becomes a new form of personally-identifying information. The public key can be thought of as a string of bytes that can be used as a “database key” in addition to being a cryptographic key. In this context, a public key can be employed to correlate and track a user's online activities across multiple online resources. For example, two web sites could compare the public keys registered at their sites, and, finding matches, could correlate the purchasing profiles of the owners of those keys in ways a user did not contemplate or sanction.

In addition, although a user will typically want to preserve his or her privacy when conducting online transactions, there are situations in which the user may want to allow web sites to share information about the user. For example, if a first web site offers discounted goods or services to members of a second web site, and the user is member of the second web site, the user may want to allow the first and second web sites to share information about the user so that the user can receive the discount.

Users therefore desire an online environment in which privacy and security concerns are addressed and in which users can control when and how online resources share user information.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

According to one aspect, a computer system includes a security module programmed to generate a first privacy key for use with secure communications with a first web site, and a second privacy key for use with secure communications with a second web site, the first and second keys being different. The computer system also includes an identity module programmed to receive a request from the first web site for linking a first user account associated with the first web site with a second user account associated with the second web site, and the identity module being programmed to present a user with an option to link the first and second user accounts.

According to another aspect, a method for communicating with a plurality of web sites includes: generating a first privacy key to communicate securely with a first web site; generating a second privacy key to communicate securely with a second web site; receiving a request for account linking from the first web site to share user information with the second web site; and presenting a user with an option to approve or disapprove of the account linking.

According to yet another aspect, a method for a first web site to link user accounts with a second web site includes: sending a request for account linking from the first web site to share user information with the second web site; receiving a response from the user approving of the account linking; and forwarding a coupon to the second web site to initiate the account linking, the coupon including a linking agreement including a first privacy key associated with the first web site and a second privacy key associated with the second web site, the first and second privacy keys being different.

DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 illustrates an example computing environment in which a computer system is programmed to communicate with a plurality of web sites using a plurality of privacy keys;

FIG. 2 illustrates example communications between the computer system and one of the web sites of FIG. 1;

FIG. 3 illustrates an example method for using privacy keys;

FIG. 4 illustrates an example coupon used to exchange user information between two web sites;

FIG. 5 illustrates an example method for implementing account linking between two web sites;

FIG. 6 illustrates an example method for a web site to request account linking with a plurality of other web sites;

FIG. 7 illustrates an example graphical user interface for presenting account linking information to a user;

FIG. 8 illustrates an example method for a web site to request and implement account linking.

DETAILED DESCRIPTION

Example embodiments will now be described more fully hereinafter with reference to the accompanying drawings. These embodiments are provided so that this disclosure will be thorough and complete. Like numbers refer to like elements throughout.

Example embodiments disclosed herein relate generally to a plurality of different privacy keys that are generated by a user's computer system for communicating securely with a plurality of web sites. Because the privacy key used to communicate with each web site differs, the use of the privacy keys cannot be used to correlate the user's activities on the different web sites. In some embodiments, the user can allow two or more web sites to share information about the user, including the different privacy keys used at the web sites.

Referring now to FIGS. 1 and 2, an example computing environment 100 includes a computer system 110, a network such as the Internet 130, and a plurality of web sites 152, 154, 156. Computer system 110 can be controlled by a user to communicate through Internet 130 with web sites 152, 154, 156.

Computer system 110 can be configured as a personal computer including at least one processor and memory. Computer system 110 includes one or more of volatile and non-volatile computer storage media, as well as removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer system 110 includes an operation system, such as the WINDOWS operating system from Microsoft Corporation, and one or more programs stored on the computer readable media.

Computer system 110 also includes one or more input and output communication devices that allow the user to interact with computer system 110, as well as allow computer system 110 to communicate with other devices, such as web sites 152, 154, 156. The user of computer system 110 can access web sites 152, 154, 156 using a program on computer system 110 such as a browser 214. One example of a browser is the Internet Explorer browser offered by Microsoft Corporation. In one embodiment, browser 214 running on computer system 110 communicates with one or more of web sites 152, 154, 156 using the hypertext transport protocol secure (“HTTPS”) protocol, although other protocols can be used.

In example embodiments, system 110 includes an identity module 216 that is programmed to maintain one or more digital identities associated with the computer user. In some embodiments, these digital identities are InfoCards that form part of the InfoCard system provided in the WINFX application programming interface developed by Microsoft Corporation of Redmond, Wash. The InfoCard system allows the user to manage multiple digital identities associated with the user, referred to as InfoCards. The InfoCard system utilizes a web services platform such as the Windows Communication Foundation in the WINFX application programming interface. In addition, the InfoCard system is built using the Web Services Security Specifications propagated at least in part by Microsoft Corporation of Redmond, Wash. These specifications include a message security model WS-Security, an endpoint policy WS-SecurityPolicy, a metadata protocol WS-MetadataExchange, and a trust model WS-Trust.

Computer system 110 also includes a security module 218 that is programmed to generate privacy keys 112, 114, 116. For example, system 110 generates privacy key 112 that is shared with web site 152. In example embodiments, privacy key 112 is a pair-wise key between the user of system 110 and web site 152. Security module 218 of system 110 is programmed to generate a different privacy key for each web site 152, 154, 156. System 110 and web sites 152, 154, 156 can, in turn, use the respective privacy key 112, 114, 116 to communicate securely. For example, system 110 can use privacy key 112 to generate an encrypted message 220 that is sent to web site 152. Web site 152 can, in turn, decrypt message 220, as described below.

Although privacy keys 112, 114, 116 are all associated with the user of system 110, each privacy key 112, 114, 116 is different. Because of this pair-wise nature, privacy keys 112, 114, 116 minimize the ability of web sites 152, 154, 156 to correlate the activities of the user of computer system 110 across the different web sites 152, 154, 156 based solely on use of privacy keys 112, 114, 116. For example, since privacy key 112, used to communicate with web site 152, differs from privacy key 114, used to communicate with web site 154, web sites 152, 154 cannot correlate the user's activities on web sites 152, 154 based solely on the keys used to communicate with web sites 152, 154.

In example embodiments, each privacy key 112, 114, 116 can be a symmetric key or an asymmetric key. An example privacy key is similar in structure to a public key, in that the privacy key is a binary number of a particular length, such as from 40 to 256 bits in length for symmetric keys and from 512 to 4096 bits for asymmetric keys. The primary difference between a privacy key and a public key is that a privacy key is not openly disseminated, but is instead sent to one or a select group of web sites. A user can have a plurality of different privacy keys, with one privacy key for each of the web sites (or each group of web sites) with which the user communicates.

In one embodiment, one or more of privacy keys 112, 114, 116 are symmetric keys based, for example, on algorithms like the Data Encryption Standard (“DES”) or the Advanced Encryption Standard (“AES”). For example, a symmetric privacy key such as privacy key 112 is known both by the user of computer system 110 and by web site 152. A symmetric key can be used to sign and encrypt, but because it is shared among system 110 and web site 152, it is not possible to determine which party signed or encrypted a particular communication. Further, privacy key 112 is not shared with a third party (e.g., web sites 154, 156), since the third party could then pose as one or both of the user and web site 152.

In an alternative embodiment, one or more of privacy keys 112, 114, 116 are asymmetric keys based, for example, on the Rivest-Shamir-Adleman (“RSA”) algorithm. In this embodiment, the user of system 110 has a secret key that is not shared, and web site 152 has privacy key 112 that can be used to encrypt messages sent to the user and to verify a signature made using the secret key. Since only the user of system 110 can sign with the secret key, it is possible for the resource to prove that the user signed a particular communication. This is commonly referred to as non-repudiation.

Additional details regarding the generation of privacy keys are described in U.S. patent application Ser. No. 11/074,885 filed on Mar. 7, 2005, the entirety of which is hereby incorporated by reference.

Referring now to FIG. 3, an example method for using privacy keys is shown. At operation 310, the user's system generates a first privacy key. The first privacy key is sent to the first web site at operation 320. For example, in some embodiments the first privacy key can be securely sent to the first web site by using the public key associated with the first web site to encrypt the message including the first privacy key. The user can then send a signed message to the first web site using the first privacy key at operation 330 (using the first privacy key if the first privacy key is symmetric or a secret key if the first privacy key is asymmetric). Next, at operation 340, the user's system generates a second privacy key, and the second privacy key is sent to the second web site at operation 350. Next, the user can then send a signed message to the second web site at operation 360 (using the second privacy key if the second privacy key is symmetric or a secret key if the second privacy key is asymmetric). In example embodiments, the first and second web sites cannot correlate transactions by the user between the first and second web sites based solely on the privacy keys used in the communications between the user and the first and second web sites because the first and second privacy keys differ.

Referring again to FIG. 1, although computing environment 100 is configured to limit the ability of web sites 152, 154, 156 to correlate information about the user of system 110 based on the keys associated with communications between the user and web sites 152, 154, 156, it may be desirable for the user to allow for correlation in some situations.

For example, if web site 152 is an airline reservations web site, and web site 154 is a car rental web site that provides discounted rates for customers of the airline reservations web site, the user may want to allow for web sites 152, 154 to share user information so that the user can receive the discounted rates.

In such situations, the user can approve account linking 158 between web sites 152, 154. Account linking allows the user to decide when information about the user on web site 152 is shared with web site 154, and vice versa. The shared user information can include profile information, such as name, address, and telephone number, as well as transactional information, such as information about the goods and/or services purchased by the user. In the example shown, account linking 158 allows web site 152 to share information about the user, such as profile and transactional information, with web site 154. In example embodiments, privacy keys 112, 114 can be used to facilitate account linking 158.

For example, in one embodiment, two pair-wise asymmetric privacy keys, “K₁” and “K₂,” are used at web sites R₁ and R₂. A human-readable policy “P” defining account linking is provided to the user for review. The policy “P” defines the way in which information will be shared between web sites R₁ and R₂. For example, the policy “P” can define what information is shared, how long the information is updated/shared, if the sharing is unidirectional or bidirectional, and what can be done with the shared information. ” S_(K) (L)” represents a signature over the content L using key K, and “T” represents a timestamp. Based on this information, security module 218 is programmed to produce a coupon “C” according to an account linking agreement “L” as follows: L={P, R₁, K₁, R₂, K₂, T}; and C=L+S _(K1)(L)+S _(K2)(L). As describe further below, the coupon “C” can be used to facilitate the sharing of user information between two web sites. In example embodiments, the linking agreement “L” is implemented as part of the InfoCard system, using an XML fragment incorporating the policy, the site identifiers, and the related privacy keys.

Referring now to FIGS. 1 and 4, an example coupon 410 is shown. Coupon 410 is a three-part extensible markup language (“XML”) document including a linking agreement 420 and signatures 430, 440 encoded over linking agreement 420 using each of privacy keys 112, 114 employed at web sites 152, 154. In some embodiments, coupon 410 can be encoded as a security token in accordance with the security assertion markup language (“SAML”) or the extensible rights markup language (“XrML”), although other languages can be used.

Coupon 410 can be used at either web site 152 or web site 154, and can be presented to the web sites 152, 154 in any order. The user of system 110 can give coupon 410 directly to each web site 152, 154, or either web site 152, 154 can forward it to the other to create account link 158. In this embodiment, non-repudiation is possible, and the user of system 110 can keep a copy of coupon 410 to indicate the policy under which the user approved account linking.

In an alternative embodiment employing symmetric privacy keys “K₁” and “K₂,” because the secret key cannot be disclosed to third parties, a second pair-wise key is introduced at each web site R₁ and R₂ that serves as an identifier, and which can be shared with selected third parties similar to an asymmetric privacy key. For example, an identifier key “I” can be used. A coupon “C” such as coupon 410 can be produced from a linking Agreement “L” as follows: L={P, R₁, I₁, R₂, I₂, T}; and C=L+S _(K1)(L)+S _(K2)(L). In this symmetric privacy key context, coupon 410 works at either web site 152, 154, and can be presented to web sites 152, 154 in any order. The user of system 110 can give coupon 410 directly to each web site 152, 154, or either web site 152, 154 can present it to the other. However, no proof is offered to either web site 152, 154 that the consumer owns the identity employed at the other web site. To obtain this assurance, web site 152 presents coupon 410 to web site 154 before linking the accounts at the two sites. Web site 154 can then verify the signature and existence of the account. Non-repudiation is not possible, since web sites 152, 154 are capable of applying the relevant signature as well as the user.

Referring now to FIG. 5, an example method 500 for implementing account linking is shown. Beginning at operation 510, the user receives a policy from a first web site regarding account linking with a second web site. Next, at operation 520, the user decides based on the policy whether or not to allow account linking. If the user chooses to allow account linking, control is passed to operation 530, and the user sends a response to the first web site approving the account linking. In example embodiments, the user's computer can generate a coupon, as described above, and forward the coupon to the first web site to approve the account linking. Alternatively, if the user decides at operation 520 not to allow account linking, control is passed to operation 540, and a response is sent to the web site disapproving of the account linking.

Referring now to FIG. 6, in some embodiments, an example method 600 allows a web site to request account linking with a plurality of other web sites. For example, beginning at operation 610, the web site forwards to the user's computer a policy and a plurality of identifiers associated with web sites with which the web site desires account linking. In example embodiments, the identifiers are public keys associated with the web sites, although other unique identifiers, such as domain names, can be used.

Next, at operation 620, the user's computer searches a list of web sites with which the user has an existing relationship to determine if any of the identifiers match any of the web sites in the list. Next, at operation 630, the policy and the list of any matching web sites are presented to the user. The user is then allowed to decide whether or not to allow account linking for any of the web sites in the matched list at operation 640. If the user decides to allow account linking for any of the web sites listed, control is passed to operation 650, and a coupon is generated including the linking agreement and a two-way signature for the selected web sites.

Alternatively, if the user decides at operation 640 not to allow account linking of any of the web sites listed, control is passed to operation 660, and account linking is not allowed for those web sites.

In example embodiments, method 600 can be implemented as part of the InfoCard system provided in the WINFX application programming interface developed by Microsoft Corporation of Redmond, Wash. The multiple digital identities stored by identity module 216 on computer system 110 can be searched when a web site requests account linking to determine if the user has existing accounts with any of the web sites in the request.

For example, in response to receiving a request from a web site for account linking with a plurality of web sites, the user's computer system is programmed to search the InfoCards associated with the user, that are stored on the user's system, that have been used to establish accounts at any of the web sites in the request. InfoCards that match the web sites in the request are presented to the user. The user can decide whether or not to allow account linking by reviewing the policy and the matched InfoCards for the web sites.

In some embodiments, account linking is implemented as part of the registration process for a web site, such as web site 152. For example, when the user registers with web site 152, the policy for the web site solicits account linking information in addition to other registration information. This account linking information can include the identifiers (e.g., public keys or domain names) of the web sites with which account linking is desired, such as web site 154. If the user has an existing account with web site 154, the user is presented with the option for account linking with web site 154 during the registration process of web site 152, and the user can approve/disapprove of account linking between web sites 152, 154. In addition, identity module 216 can be programmed to allow the user to track which sites the user has approved for account linking.

For example, referring now to FIG. 7, during the registration process with web site 152, the user is presented with a graphical user interface 700. User interface 700 can be presented within browser 214 or as a separate interface on computer system 110. Interface 700 provides a window 610 with a list of all of the web sites with which web site 152 requests account linking and the user has an existing relationship. For example, window 610 lists web site 154 for which account linking is requested by web site 152 and with which the user has an existing account. The user can authorize account linking for web sites 152, 154 by checking box 620. Alternatively, the user can disallow account linking by leaving box 620 unchecked and continuing with the registration process for web site 152. If multiple web sites are listed in window 610, multiple check boxes can be provided so that the user can select with which, if any, web sites to allow account linking.

Referring now to FIG. 8, an example method 900 for a first web site to request and implement account linking is shown. At operation 910, the first web site sends a request for account linking to a user. Next, at operation 920, the web site receives the response from the user. At operation 930, the web site determines if the user has approved of account linking. If account linking has not been approved, control is passed to operation 950, and account linking is not implemented.

Alternatively, if account linking is approved by the user, control is passed to operation 940, and the first web site evaluates the coupon received from the user to verify the signatures in it, such as coupon 410 described above. Next, at operation 960, the first web site exchanges the coupon with the second web site to implement account linking and to obtain profile information about the user from the second web site.

In example embodiments, the first web site can exchange a coupon with the second web site using the protocols defined in the web services platform such as the Windows Communication Foundation provided in the WINFX application programming interface developed by Microsoft Corporation of Redmond, Wash. For example, the first web site can forward a coupon and profile information to the second web site by sending a request security token (“RST”) in accordance with the issuance mechanism provided in WS-Trust. An example RST including a coupon is shown below. <RequestSecurityToken> <TokenType> urn:...:TokenType:AccountLinking </TokenType> <Claims> <Claim URI=“http://.../account-linking/claims/AccountId”/> <Claim URI=“http://.../account-linking/claims/MembershipLevel”/> <Claim URI=“http://.../account-linking/claims/MembershipStatus”/> </Claims> <AccountLinkingAuthorizationToken> [Coupon from user that authorizes account linking is inserted here] </AccountLinkingAuthorizationToken> </RequestSecurityToken> The second web site can respond to such a request by sending a request security token response (“RSTR”) back to the first web site, an example of which is provided below. <RequestSecurityTokenResponse> <TokenType> urn:...:TokenType:AccountLinking </TokenType> <RequestedSecurityToken> <AccountLinkingToken> [Custom token containing account linking information is inserted here] </AccountLinkingToken> </RequestedSecurityToken> </RequestSecurityTokenResponse> In example embodiments, the security tokens issued by the first and second web sites can be generated in one or more of a plurality of formats including, without limitation, X509, Kerberos, SAML (versions 1.0 and 2.0), Simple eXtensible Identity Protocol (“SXIP”), etc.

One or more advantages are associated with the systems and methods described herein. For example, the use of privacy keys can enhance the privacy of users in the online environment. Further, the use of account linking allows users to decide when and how information associated with the users is shared between web sites.

Although the examples described herein reference web sites, in alternative embodiments, privacy keys and account linking can be used with other online resources as well. For example, in alternative embodiments, rich client applications accessing web services over the Internet using the Web Service standard protocols defined in the WS-* suite can utilize privacy keys and account linking. For example, in one alternative embodiment, a dedicated rich client application that allows a user to trade stocks and manage a portfolio with a brokerage can initiate account linking between the brokerage account and the user's bank account. Other alternatives are possible.

The various embodiments described above are provided by way of illustration only and should not be construed to limiting. Those skilled in the art will readily recognize various modifications and changes that may be made to the embodiments described above without departing from the true spirit and scope of the disclosure or the following claims. 

1. A computer system comprising: a security module programmed to generate a first privacy key for use with secure communications with a first web site, and a second privacy key for use with secure communications with a second web site, the first and second keys being different; and an identity module programmed to receive a request from the first web site for linking a first user account associated with the first web site with a second user account associated with the second web site, and the identity module being programmed to present a user with an option to link the first and second user accounts.
 2. The computer system of claim 1, wherein the security module is further programmed to generate and forward a coupon to the first web site in response to the user approving of the linking, the coupon facilitating the linking of the first and second user accounts.
 3. The computer system of claim 2, wherein the coupon includes a linking agreement including the first and second privacy keys.
 4. The computer system of claim 1, wherein the request for the linking of the first and second user accounts from the first web site includes a policy defining how information in the first and second user accounts will be shared between the first and second web sites.
 5. The computer system of claim 1, wherein the request from the first web site includes requests for linking accounts from a plurality of web sites, and the identity module is further programmed to search for digital identities on the computer system that match one or more of the plurality of web sites.
 6. The computer system of claim 5, wherein the identity module is further programmed to present the user with options for linking user accounts associated with matching digital identities.
 7. A method for communicating with a plurality of web sites, the method comprising: generating a first privacy key to communicate securely with a first web site; generating a second privacy key to communicate securely with a second web site; receiving a request for account linking from the first web site to share user information with the second web site; and presenting a user with an option to approve or disapprove of the account linking.
 8. The method of claim 7, further comprising: generating a coupon in response to the user approving of the account linking, the coupon facilitating the account linking; and forwarding the coupon to the first web site.
 9. The method of claim 7, wherein the request from the first web site includes requests for accounts linking for a plurality of web sites, and the method further comprises: searching for digital identities associated with the user that match one or more of the plurality of web sites; and presenting the user with options to approve or disapprove of the account linking for web sites with matching digital identities.
 10. A computer-readable medium having computer-executable instructions for performing the steps recited in claim
 7. 11. A method for a first web site to link user accounts with a second web site, the method comprising: sending a request for account linking from the first web site to share user information with the second web site; receiving a response from the user approving of the account linking; and forwarding a coupon to the second web site to initiate the account linking, the coupon including a linking agreement including a first privacy key associated with the first web site and a second privacy key associated with the second web site, the first and second privacy keys being different.
 12. The method of claim 11, further comprising receiving the coupon from the user.
 13. The method of claim 11, further comprising verifying the coupon.
 14. The method of claim 11, wherein sending the request further comprises sending the request for the account linking during a registration process of the first web site for the user.
 15. The method of claim 11, wherein sending the request further comprising sending a policy to the user, the policy defining how the user information is shared with the second web site.
 16. A computer-readable medium having computer-executable instructions for performing the steps recited in claim
 11. 